home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
cback1.zip
/
CALLBACK.DOC
< prev
next >
Wrap
Text File
|
1991-12-01
|
16KB
|
439 lines
Callback Verification Version 1.52
Copyright (C) 1991 By Axis Developments
Programed By Robert Goshko
Calanost BBS - (403)474-5579
FidoNet - 1:342/29
RBBSNet - 8:990/107
CompuServe - 70740,3640
Callback V1.52 Page 2
Table of Contents
-----------------------
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . Page 3
1.1 Kudos . . . . . . . . . . . . . . . . . . . . . . . . . Page 3
1.2 Warrenty. . . . . . . . . . . . . . . . . . . . . . . . Page 3
1.3 FOSSIL Note . . . . . . . . . . . . . . . . . . . . . . Page 3
2.0 SetUp. . . . . . . . . . . . . . . . . . . . . . . . . . . Page 4
2.1 Configuration Commands. . . . . . . . . . . . . . . . . Page 4
3.0 The Command Line . . . . . . . . . . . . . . . . . . . . . Page 6
4.0 Interfacing Callback . . . . . . . . . . . . . . . . . . . Page 6
4.1 With Maximus-CBCS . . . . . . . . . . . . . . . . . . . Page 7
4.2 With RBBS-PC 17.x and up. . . . . . . . . . . . . . . . Page 8
4.3 With XBBS 1.17. . . . . . . . . . . . . . . . . . . . . Page 8
4.4 Other BBS Systems . . . . . . . . . . . . . . . . . . . Page 8
5.0 SysOp Keys . . . . . . . . . . . . . . . . . . . . . . . . Page 9
6.0 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . Page 9
7.0 Registration . . . . . . . . . . . . . . . . . . . . . . . Page 9
Callback V1.52 Page 3
1.0 Introduction
Welcome to the Callback user verification program. I wrote this
program mainly because of all the callback verifiers that exist, I was
never able to find one that would work with anything above COM2 on a
standard IBM system. Since my BBS used an internal modem on COM4, I
could never get one to work. With a good knowledge of C and Ray
Gwinn's FOSSIL developers guide in hand, I give you this.
Callback was writen and tested with Ray Gwinn's double aught
buckshot driver version 1.24. The two other FOSSIL's I know about are
BNU and OpusCOMM, and I cannot say if it will work with either one.
1.1 Kudos
There a a few people I would like to thank and they are as
follows:
Raymond L. Gwinn - Developer of the FOSSIL specification and one heck
of a FOSSIL driver.
Sean M. Pratz - SysOp of Wrigley Field. Supplied the internal
structure of the JUMPER.DAT file, and offical beta
tester.
Scott J. Dudley - Creator of Maximus-CBCS. Supplied the internal
structure of the DOOR.SYS, CHAIN.TXT, and
CALLINFO.BBS files.
Don Hazlewood - SysOp of Satellite RBBS-PC. Tested the built in
RBBS-PC interface.
1.2 Warrenty
This program and it's supporting files will take up room on your
harddrive or floppy disks until you delete it.
1.3 FOSSIL Note
Callback is totally FOSSIL driven, so if you do not currently
have a FOSSIL driver installed on your system, you will need one.
Callback does not initalize the FOSSIL, it just continues using
it at the rate that the BBS set it to.
Callback V1.52 Page 4
2.0 SetUp
Create a directory and unzip the files in to the directory you
wish to use. There are 4 files included in the package that you
must have all in one place, they are as follows:
CALLBACK.EXE - The actual program
CALLBACK.CFG - The configuration file
INFO.TXT - Operating instructions for the user
BADNUMS.TXT - Numbers the you don't want called
Those are all the default filenames, the last two (INFO.TXT and
BADNUMS.TXT can be changed via the configuration file. The fifth and
final file that will be made the first time someone is verified is on
called VERIFY.TXT. This will contain the names of the users that have
been verified and their phone numbers. Callback will not verify two
people with the same phone number.
2.1 Configuration Commands
The configuration file CALLBACK.CFG must reside in the smae
subdirectory as the executable. This file is a flat ASCII file so you
can edit it with Qedit or any other text editor. Don't use a word
proccesor, because many of them insert control characters and other
garbage into a file and that will confuse the executable.
Any line starting with a semi-colon (;) will be treated as a
comment, and will be skiped.
PORT <FOSSIL port #>
This command word specifies which FOSSIL port the program will
use for serial I/O. The FOSSIL port must be initalized to the BAUD,
parity, word length and stop bits prior to running the program. The
FOSSIL port number is ONE LESS than the COM port number, COM1 is
FOSSIL port 0, etc...
VERIFIED <File Name>
This command allows you to specify the file that Callback will
write the names and phone number of users to, for it's own use. For
logging information see the LOG command word.
BADFILE <File Name>
This command specifies which file contains the number that you do
not want your computer to call. The number in this file support the
wildcard ?, for blocking numbers like 911, you would enter ???911????.
Since the area code and postfix are irrelevent, any number begining
with 911, will not be dialed.
Callback V1.52 Page 5
INFOFILE <File Name>
This command word tells Callback to display this file to the
caller after the welcome and before any information is asked of the
caller. It is a flat ASCII file with no ANSI codes.
AREACODE <Three digit area code>
This lets Callback know what your local area code is. Callback
will not verify people who are calling long distance, because I am not
wealthy enough to support this, and I don't know any SysOp that is.
AREANAME <Name>
This is the name of the area that your area code covers, my area
code of 403 covers the province of Alberta so I have Alberta listed as
the area name.
DIAL <ATDT or ATDP>
This is the dial command used by your modem, ATDT for touch tone
dialing, or ATDP for pulse tone dialing.
BBSNAME <Name of BBS>
This command set your BBS name display within Callback and to the
user.
SYSOPNAME <SysOp's Name>
This specifies the SysOp of the BBS, or the person you may have
delegated to take care of any user verification problems.
(optional) LOG <Path\File Name>
The LOG command word is used to specify a file that Callback will
log any error's or verifications to. The log format used is the same
a BinkleyTerm and Maximus. This command word may also have a complete
path to a log file after it (eg. LOG E:\MAX\MAX.LOG). Log entries
will look like this:
! 26 Nov 14:56:41 CBAK Verification of USER : TEST USER1
! 26 Nov 14:57:43 CBAK TEST USER1 Verified at xxxyyyzzzz
Callback V1.52 Page 6
3.0 The Command Line
The command line call for Callback includes 2 major components
for all BBS types and an extra for BBS's using the RBBS-PC style
DORINFOx.DEF file. The standard form is as such:
CALLBACK <door type> <path to door file> [node]
<door type> is any of the following:
DORINFOx - RBBS/QuickBBS style DORINFOx.DEF file
JUMPER - 2AM-BBS JUMPER.DAT file
CHAIN - WWIV BBS CHAIN.TXT file
DOOR - GAP BBS DOOR.SYS file
CALLINFO - Wildcat BBS CALLINFO.BBS file
<path to door file> is the full path, including trailing backslash to
the directory where the door file is located.
[node] is only needed if you are running a system with the
DORINFOx.DEF type of door interface file.
4.0 Interfacing Callback
Callback does not change the user's security level within any BBS
user files, this still remains the concern of the SysOp, or the
designated party. Callback will exit with a DOS errorlevel of 1 if
the user was verified, and a DOS errorlevel of 0 if the verification
failed (long distance, no contact, or failed code reentry).
Callback V1.52 Page 7
4.1 With Maximus-CBCS
Included in this archive is a file named MAXIMUS.xxx, this file
contains the .BBS and .MEC files that I use for interfacing Callback
and Maximus. I have the two .BBS files (NOGOOD.BBS and GOOD.BBS)
located in my \MAX\ directory and this in my MAX.BTM (4DOS batch
file):
.
.
.
if errorlevel 250 goto callback
.
.
.
:callback
callback.exe dorinfo e:\max\ 1
if errorlevel 1 goto verified
copy e:\max\nogood.bbs e:\max\misc\afterver.bbs
goto ONLINE_DOOR { restart Maximus }
:verified
copy e:\max\good.bbs e:\max\misc\afterver.bbs
goto ONLINE_DOOR { restart Maximus }
You can see that if the user is verified, the AFTERVER.BBS file
in my \MAX\MISC\ directory will contain the MECCA commands to increase
the user's security level. If not, the the NOGOOD.BBS file will be
displayed.
Calling Callback from a MECCA file, you can use these MECCA
commands, as long as the file that calls them are located after the
NEWUSER2 file is displayed to the user:
[link]Misc\dorinfo
[Dequal][xtern_erlvl]250
[Nline][goto end]
[link]Misc\AfterVer
[label end]
Callback V1.52 Page 8
4.2 With RBBS-PC 17.x and up
The archive labeled RBBS.xxx will contain only one file,
CALLRBBS.CFG, this file contains only one command word, ADD2SECLVL.
The value following this command word will be ADDED to the new users
existing security level. If this file (CALLRBBS.CFG) is located in
the same directory as CALLBACK.EXE and you are using the DORINFO
command line parameter, Callback will make the file DOUTx.DEF in the
directory specified on the command line. This file is used by RBBS-PC
to change the current user's security level.
You enter CALLBACK.EXE in parameter 107 in the RBBS-PC
configuration program if all your Callback files are in the RBBS-PC
default directory. If not, you will have to write a batch file to
change to your Callback directory.
4.3 With XBBS
If you are using the XBBS package, you can include these lines in
your WELCOME.XBS file (REMEMBER the @ symbol represents the 0x01
character {little smily face} ):
@S>90 lUserOK
@X0
@ESCALLBACK.EXE dorinfo e:\xbbs\ 1
@e==1 lVerified
Sorry @uN, but you have not been verified.
@blUserOK
@lVerified
@-910-010
Congrats @uN, you have been verified.
@lUserOK
This checks the user's #9 security level, if it is grater than 0,
the user has already been verified, and the callback is skiped. If
not, Callback is called (without unloading XBBS) and ran, if the user
is sucssesfully verified, security level #9 is changed to 10, and
security level #0 is changed to 10.
If you have tight memory requirements, you can use the @EE
function to run Callback from the .XBS file.
4.4 Other BBS Systems
Callback was made so it could run off of a variaty of BBS
systems, unfortunatly I have currently only ran three types of BBS
packages. If you are running a BBS package not currently listed, you
could send me the type, version, and how you interfaced Callback with
your system, I will include your adaptation in the next release.
Callback V1.52 Page 9
5.0 SysOp Keys
The local keyboard has 6 special function keys for use by the
Sysop, they are as follows:
F1 - Displays a small menu of the local keys (local only)
F3 - Raise the users online time by 1 minute.
CTRL F3 - Raise the users online time by 5 minutes.
F4 - Lower the users onlint time by 1 minute.
CTRL F4 - Lower the users online time by 5 minutes.
ALT C - Enter/Exit Chat with the user.
6.0 Conclusion
If you have any questions, suggestions, or comment's feel free to
contact me at one of the addresses on the cover or via my BBS. If you
wish, send me a copy of the BBS file you want Callback to work with
and I will modify the next version.
7.0 Registration
Just fill out the form on the next page and mail it to:
Robert Goshko
c/o Axis Developments
3408 - 105 Avenue
Edmonton, Alberta
T5W 0B4
Canada
Callback V1.52 Page 10
Callback Registration Form - Version 1.52
P L E A S E P R I N T O R T Y P E
SysOp Name : ______________________________________________________
BBS Name : ______________________________________________________
BBS Software : ______________________________________________________
BBS Number : (_______) _______ - __________
Voice Number : (_______) _______ - __________
Address : ______________________________________________________
City/Town : ______________________________________________________
Province : ____________________
Postal Code : ____________________
Are you a member of Fidonet [_] or RBBSNet [_] (Check All That Apply)
FidoNet Address : _______________ RBBSNet Address : _______________
Registration Method:
___ $11.00 Registration Key Sent Via Netmail ............ ____.______
(Just the key file)
___ $13.00 Registration Key Sent Via Canada Post ........ ____.______
(Latest Version of Callback & key file)
___ $15.00 Registration Key Sent Via Netmail ............ ____.______
(Latest Version of Callback & key file)
Total = ____.______
Payment Method: Cheque [_] Money Order [_] (Check One)
Signature __________________________________________ Date ___/___/___